OpenEdge Data Management:<br />DataServer for Microsoft SQL Server Configuring with the Progress Explorer

In Windows, you can use the Progress Explorer tool to configure the DataServer for MS SQL Server.

Make sure that the AdminService is running.

Start the Progress Explorer. From the Windows Desktop choose Start

Programs

OpenEdge

Progress Explorer Tool. The Progress Explorer appears in the MMC framework.

Connect to localhost.

From the Progress Explorer’s left pane, select the MSS DataServer folder and double-click. The list of existing DataServer brokers for MS SQL Server appears in the right pane.

Select the DataServer instance whose properties you want to create or edit, and right-click. A pop-up menu appears.

Note: The DataServer for MS SQL Server installation provides one predefined DataServer Broker (mssbroker1) and one predefined NameServer (NS1). Each broker is referred to as an instance. See the Progress Explorer online help for more information. You can use these predefined components as a starting point for creating and configuring additional DataServer Brokers, and, if needed, NameServers. (See OpenEdge Getting Started: Installation and Configuration for information about the NameServer’s role in a configuration.)

Choose the Properties option from the pop-up menu. The Properties dialog box for that instance appears.

Configure the DataServer broker by setting general DataServer properties, owner information properties, application service properties, logging settings, environment variables, and others. For details on these settings, see the Progress Explorer online help.

Note: By default, your DataServer for MS SQL Server broker instances are defined with a controlling NameServer and are provided with a default Data Service. Progress Software Corporation recommends using a NameServer configuration at all times. In such cases, the DataServer client’s initial connection is to the NameServer. However, you can alternatively connect the DataServer directly to the broker instance by setting the -DataService value to none in the connection parameters of your schema holder, or by adding the -DirectConnect parameter which will override your -DataService parameter. If you will always use a -DataService value of none, you should remove the controlling NameServer from your broker instance definition. See the "Starting and stopping a broker process from the Progress Explorer and connecting a client" section for more information about connecting the DataServer to the NameServer and the broker.

Do not simultaneously run some DataServers for MS SQL Server under brokers with controlling NameServers and others directly under brokers (that is, without controlling NameServers). This defeats the purpose of using a NameServer to control brokers. If you do this, the benefits of the NameServer are lost and load balancing is ineffective. Progress Software Corporation recommends that you always use a NameServer, with one exception: you can choose initially to connect directly to a broker to simplify confirming an initial connection. Once you establish a connection, Progress recommends that you reintroduce the NameServer into your configuration.

Once you have completely set up your environment, you can build the schema holder for your MS SQL Server database. See the "Creating a schema holder" section for instructions.